Hello.

I've got a computer in my work that have randomly have "Document not saved" when trying to save excel files on the local network. In periods It happen everytime she' tryin to save, but It most happen like now and then.

She had the same problem when having Office 2007. I'd hope It was a Office 2007 issue, but when upgraded to Office 2010 It happens often as before.

I've have been tryin some hotfixes and some other tricks for Office 2007.

Computer: HP Elitebook 6930p with Windows 7 enterprise x86, office 2010 Pro

Hi,

 

There is a KB article taking about the problem when saving Excel files to network location. Please check if it helps:

 

You receive an error message when you save a file after the network connection is lost in Excel

http://support.microsoft.com/kb/291204

 

If the problem persists, you can also troubleshoot the issue by the suggestions here:

How to troubleshoot errors when you save Excel files

http://support.microsoft.com/kb/271513

 

Hope it helps.

 

Best Regards,

 

Sally Tang

Hi.

I have tried the solution mention in the KB article, but no. Its only one computer who got this problem, in environment with 50 computers. Can't find any signs on software failure either.

Have also tried this hotfix: http://support.microsoft.com/hotfix/KBHotfix.aspx?kbnum=983458&kbln=en-us

Here is what event viewer said about It.

Microsoft Excel

Document not saved.

P1: 100490

P2: 14.0.4763.1000

P3: xsmh

P4: 0x80070499

I have a user with the same problem.  Only noticed problem when we upgraded from Office2003 to Office2010.  Only appears to be an issue with saving to her J drive which is a network drive.  We can save to other network drives.  Can save to local pc.  I have checked and reset permissions to full control on that drive/folders.

Error below... I'm very perplexed and determined to find out what is wrong.  This computer is the ONLY one out of about 40 who have this problem.  I did notice some Event 1003 licensing errors in the Application log... could this be something>

Help!

Event Type: Information
Event Source: Microsoft Office 14 Alerts
Event Category: None
Event ID: 300
Date:  10/13/2010
Time:  5:13:25 PM
User:  N/A
Computer: ECANNING-
Description:
Microsoft Excel
Document not saved.
P1: 100490
P2: 14.0.4763.1000
P3: xslr
P4: 0x80070497

Seeing the same issue on multiple Win7 / Office 2010 machines, saving to network Share.  Error "Document not saved" occurs in Excel upon first save, usually will save successfully on second and subsequent attempts.  Happens locally and remote via VPN.  Restart Excel, and first save fails again.

Office Event Log:
Microsoft Excel
Document not saved.
P1: 100490
P2: 14.0.4763.1000
P3: xslr
P4: 0x80070497

 

I've been through the above troubleshooting procedures - none of them describe this issue.  I have a <simple> test Excel spreadsheet with only text and can reproduce the "Document not saved" error at will.  It does occur in Word, but not as consistently.

Have tried HOT FIX KB983458 for KB980232 and removing both of them w/o resolution:

http://support.microsoft.com/kb/980232
http://support.microsoft.com/kb/983458

Removing Antivirus (Trend) did not resolve.

Any help appreciated!

 

Remove the KB980232 Microsoft update, which requires a restart.

Remove the KB979683 Microsoft update, which requires a restart.

Hi There,

 

We are also experiencing the same problem on our network. None of the kb articles helped and I was hoping that someone has discovered a fix for this? It happens in any Excel format and at random times.

Still happen's - Is there ain't any solution yet?

Having exactly the same issue here. Only one user and intermittent as well. Any joy as yet?

Same problem here.  Smaller network (only 15 computers), but one unique machine with issue.  Very vexing.  Heavy Excell user - this is a big problem for this person.  On some occassions, after first save fails, the file shuts down and is lost (no opportunity to try second save).  TEMP file is all that's left. 

This started with older version (2000) and continued with 2010 upgrade.  Files reside on shared drive and were originally created in older version.  MS support thought it was Trend Micro getting in the way - but alas, not correct, problem persists.  This workstation was new this summer and worked great without issue until this problem started maybe a couple months back - I suppose just about the date of TotalRandomGuy's post.  Did everyone start having issues around the same time?

Thought I'd mention that just like Bharston (above), we show a bunch of Event 1003 licensing errors in the Application log.  Anyone else?

Just moved files he's workin on from the shared drive on the server (Small Business 2003) to person's local c: drive.  It's only been a couple hours, but can't re-create the problem now.  This is not ideal solution, but seems to work for time being.  We'll keep our eye on it and report back if we learn anything further.

Does this help point in the right direction?

I, too, am having this problem since obtaining new computer with Windows 7 and Office 2010.  Files are not saved to a network but directly on C drive.  It happens on Excel sheets I have created and also those e-mailed to me that I need to save.  I have been leaving my machine on with the files open so as to not lose the information.

Any help would be appreciated.

Any updates on this, This problem is becoming really tedious. These are the steps I have followed\done so far.

 

1) Office 2007 Repair.

2) Made sure that KB980232 and KB979683 were not installed

3) Installed Hotfix as recommended KB983458 no success.

4) Tried with multiple users on same machine, error occurs on multiple users.

5) Made sure that the user has full permissions to the file.

6) Created the two registry entries, NetworkResiliency and PivotTableNetworkResiliency.

I have probably done a couple more steps but forgot along the way.

 

Just to re-cap the symptoms again.

 

I open up a document which is stored on a mapped network drive. When I try to save the document I intermittently get an error saying document not saved ID 1000490(ctrl + shft+ I). When I close the document the original file will be gone and a temp file will be there. 8 characters in length (A2JGF84V.TMP). If I rename the file to the original name and change the extension to .xls I can open the document fine. Saving as a different name does work, but not an acceptable solution, saving the the local HDD does work, but once again not an acceptable solution. I have ran ProcMon and cannot find any issues at the time of trying to save the document. Any help would be much appreciated.

 

Regards,

 

Warren

I have the exact same problem.

Office 2007 and 2008 R2 server.

We also have this intermittent problem when trying to save an Outlook attachment to a network folder. We get the error message "Cannot save attachment" - an empty .tmp file is created instead of the file I want.

We just moved to an R2 server when these problems started. On the old 2003 server, we never saw anything of these issues. My guess is that it's a privelege problem on the server and not related to the client at all..

The above mentioned hotfixes have made no change.

Not that this helps, but I am having this issue with a few users.  Just started migrating users to Windows 7 and Office 2010.  Did not see this issue on XP or Office 2003.  Same problem as described above, get "document not saved" error, and notice that Excel.exe 32 process is still running, even though Excel has been closed.  I can't seem to kill the process and end up having to reboot the machine.

Would like to see this resolved.

Mike

 

Found this, this morning.  Anyone tried it and does it fix this problem?

Mike

 

http://support.microsoft.com/kb/983458

No fixes yet! - Personaly have I gived it up. Installed a Vmware VDI client to the user with the problem. It seems like a network problem of something.

TRG,

I hate to ask, but did you try the hotfix I listed above?  I have installed it on one computer having this problem and am waiting to see if it fixes it, but I won't know if a day or two I'm sure....

 

Mike

I hate to ask, but did you try the hotfix I listed above?  I have installed it on one computer having this problem and am waiting to see if it fixes it, but I won't know if a day or two I'm sure....

Hey - have been looking for a solution for this!

One of my work laptops started having this problem, (Windows 7, Office 2010) and couldn't fathom it out. Downloaded 983458 from the MS Website and the password didn't work, (odd), anyway, I then downloaded it from:

http://thehotfixshare.net/board/index.php?autocom=downloads&showfile=12254

And hey presto! Problem solved! Thanks so much for pointing this in our direction!

You're a star

Ian

Ian,

That is great.  It seems to be working for me as well on one one user, but will test some more today.  Glad it helped you!

What I am a bit perplexed by, is this seems to be a fairly widespread problem with what I have been reading about after finding the offending KB980232, and why, after almost a year of that updated being put out has the fix for this not been rolled into a automatic update instead of a hotfix you have to go look for?

 

Mike

This seems to be a tricky problem.  For us it is intermittent, only on Excel workbooks, and for what it's worth only on shared-mode workbooks.  Anecdotally it seems more problematic on Excel 2010, but I can't say for sure it doesn't happen on Excel 2007.  We have both installed.  But it was never reported until upgrading clients to Win7 x64 and adding Office 2010.

If I understand correctly, our client (Win7 x64 & some XP SP3 x86) plus file-server (2003 x86 SP2) environment doesn't fit the environment described for hotfix KB983458.  IE I have no SMB 1.0 component right?  Would one SMB 1.0 device on the LAN affect all servers?  EG a WAP, phone system controller, SPAM appliance etc?  Is there any way I can tell if SMB 1.0 is in use?

As further evidence that KB983458 my not be the fix, KB980232 was installed on the file-servers Apr-'10, and we didn't start experiencing problems until moving to Win7 x64 + Office 2010 x86 in Oct-'10.  As mentioned above we experience the problem less (not at all?) on Excel 2007.  So far we've retreated to Excel 2007 by unenforced policy, but occasionally users stumble into Excel 2010 accidentally and that seems to be when we experience the missing document plus abandoned temp file, or the message "Document cannot be saved".

At the risk of thrown tomatoes: how bad is to have a mixed Office 2007 / 2010 enviroment?  Especially with shared-mode Excel workbooks?

For now I'm planning on enforcing the no-Excel-2010 policy, but I'm not convinced that's a complete fix.

Hank

Make sure you user account control  is disabled or turned off on vista or windows 7. that has fixed my issue.

 

many thanks

reddy

I solved my "document not saved." problem by copying all the sheets to a different workbook and then saved as successfully. 

Hi,

We had the same issue,normally opening the 2003 files but when we converted those files to 2010 the issue is not there any more.

Hope this helps..

Hi guys,

I resolved my same problem. I have windows 2008 server r2 and windows 7 pro station whit office 2010.

My problem was from a settings from GPO "Files not cached" where i put *.tmp

After i change it to "Not configured" and my office can save on the network again

Try to see if u have the settings active and remove it.

After long struggle I decided to Save As new workbook, and it worked!
Thank you very much for your suggestions

I was having the same problem, only seemed to impact Excel 2010 (not earlier versions) saving to a Samba shared folder though.

I found this KB, which has fixed the problem for us, hope it is useful to you. It has to do with how Excel creates a temp file to save changes and then tries to delete the file.

http://support.microsoft.com/kb/2589410

I see.

Here are some methods for your reference:

Method.1

Give the users Delete permission, in the mean time, set a backup folder that will regularly backup the documents from the original folder.

Method.2

Follow the instructions in the following support article http://support.microsoft.com/kb/2589410/en-us

Install the hotfix to the client computers, and also add the registry subkey "EnableSimpleCopyForSaveToUNC".

As it stated, when users do not have Delete permissions for the UNC share, the temporary copy of the original document is not deleted after save the document.

PS. The support article is for Excel 2010, but also applies to Word.

After painfully searching for a solution to this issue, I decided to try to copy the original and then delete it and rename the copy to what ever the original file name was and it worked.  I'm not sure that if copying and deleting the original file killed whatever was causing the issue or not, but it worked and I can save changes to the spreadsheet as normal. 

Hello,

I opened my excel file from a network drive over Ethernet.

When I connect my laptop to the WiFi and trying to save the file, I receive the same error message.

I tried to connect back to the Ethernet - and disconnecting the WiFi - the file is save successfully!

I hope this helps.

Karim

I've try to install a few hotfixes but not working,our situation is only one laptop has problem. It's nothing with user permission, user log on to another compter, he can save to same network drive. I use my account to log on his computer, can't save as well. So we think just that computer's problem. Of course we can save to the local drive then copy to there, but it's not user wants.

Finally we fix it by create new shared name for the same share folder, and re-map it with new shared name. But I don't what's root reason, if anyone knows please post it. Thanks.

Hope it can help!

I have suddenly developed the same problem.

I saved the file with a different name (which worked), and all good again.

I can only assume that someone else attempted to open the file at the same time as me and it caused an issue.